Release 10.1A: OpenEdge Data Management:
DataServer for Microsoft SQL Server

Local schema caching

By using a local file to store schema definitions, you can access them more quickly. Running DataServer applications with a local schema cache can result in better performance in networked environments.

The Progress 4GL SAVE CACHE COMPLETE statement creates a binary file that contains the entire schema for an OpenEdge database. Use this statement to create a cache file for a connected schema holder:

SAVE CACHE COMPLETE schema-holder-name TO filename.

For example, the following statement creates a cache file named sqlcache for the sqlhold schema holder:

SAVE CACHE COMPLETE sqlhold TO sqlcache.

To use the cache file specify the Schema Cache File (-cache) startup parameter and the cache filename when you connect to the schema holder. For example, the following CONNECT statement connects an MS SQL Server database whose data source name is sqlbdb with the schema sqlhold and tells OpenEdge to use the cache file sqlcache:

CONNECT sqlhold -RO -db sqlbdb -dt MSS -ld sqldemo -U bob -P bobpass -Dsrv qt_debug,EXTENDED, -cache sqlcache.

If you make any changes to a schema holder, you must create a new cache file for it. For more information, see the “SAVE CACHE Statement” reference entry in OpenEdge Development: Progress 4GL Handbook .